Notes/Domino Fix List
 |  |
| SPR # PSON5EST8U | Fixed in 6.0.2 release |  |
Product Area: Server Technical Area: Serviceability Platform: Windows
SPR# PSON5EST8U - This fix allows an notesnsd.ini to be created in the data directory if necessary. If the user has insufficient privileges to create %SystemRoot%\notesnsd.ini then it will be created in the data directory instead. The drawback is that multiple notesnsd.ini files could be created.
Technote Number: 1115742
Problem:
This issue was reported to Quality Engineering and has been fixed in Domino
6.0.2. The 6.02 version of NSD will use the current Notes data directory as a
location for the notesnsd.ini file if access to the WINNT directory is
restricted and the file not found.
Excerpt from the Lotus Notes and Domino Release 6.0.2 MR fix list (available at
http://www.lotus.com/ldd):
Serviceability
SPR #PSON5EST8U - This fix allows an notesnsd.ini to be created in the data
directory if necessary. If the user has insufficient privileges to create
%Systemroot%\notesnsd.ini then it will be created in the data directory
instead. The drawback is that multiple notesnsd.ini files could be created.
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
Workaround:
If running a previous release of Notes, this problem can be avoided one of
several ways.
You could modify the WINNT directory and give all users full create/modify
access at the directory level. However, this defeats part of the purpose of
having a locked down secure client.
A more secure solution is to create (under an Admin user) the notesnsd.ini file
(it can be zero length) and then adjust the security of the file so the
appropriate group has full access (write/modify). This could be done
programmatically, via Windows APIs, or manually as described below.
Creating the NSD configuration file
1. First, you must create and save a blank notesnsd.ini file using either
option A or B .
option A: via Notepad... notepad c:\WINNT\notesnsd.ini
option B: using the command string TYPE c:\WINNT\notesnsd.ini >
c:\WINNT\notesnsd.ini (since the file does not exist, this command will
create a zero length (null) file.)
2. Once the zero length file exists, from Windows Explorer, open the
Properties box for the file and grant the Users group Full Control.
3. Reply OK to save the modified permissions
4. Return the machine to the user's Windows ID
After following these steps (from an Administrator level User), a restricted
user should be able to run NSD successfully.
Supporting Information:
The limited user workstation prevents the application from creating
notesnsd.ini, doing a memcheck on the computer and reporting this to the log.
In a Notes R5.x environment, users must be given administrative access to the
workstation or enable QNC as the default debugger.
Optionally, giving all users the policy "Debug programs" (which was not defined
by default) will partially solve the problem. The NSD runs when activated
manually.
More >
Last Modified on 05/18/2007
Go back
|